Integrate task execution, Computers, mobile workflows, and qualification fixes - #27

Operators need to select a computer, follow a task, and inspect its approval and execution outcome from Buzz. This candidate connects mobile Work and Computers to durable task, permission, dispatch and receipt records, while preserving the upstream relay, desktop and mobile codebase.

Candidate head f81e81f2242790bc62992612d22ce18ee470ca8a targets product/main at adeec6eb5c4ff425aa03d8a744a295da4429f67f. The complete diff spans 259 files and requires independent review as a whole. Local inclusion is not an individual GitHub PR merge.

The latest repairs make mobile task refresh respect pagination, visibility and lifecycle; wait for actual Redis subscriber readiness; bind task notifications to the authenticated session and verified delegation; and keep urgent disconnects responsive while task permission queries are blocked. Duplicate notifications coalesce, bounded overflow and missed control messages require fresh authorization. The desktop slow-response fixture establishes body progress without weakening the operation deadline. PostgreSQL CI now supplies the Redis test URL, and the desktop lockfile includes the shared WebSocket client's existing UUID dependency.

Validation on this candidate:

• Full local just ci completed with exit 0 on the exact head and a clean checkout, including 2,334 Flutter tests. Filtered and ignored cases are not counted as passes.
• Canonical PostgreSQL verification passed on the same exact head: 458 passed, 0 failed, 1,500 lane-selected skips. The run includes signed task-notification and workflow-approval HTTP/database flows. Skips are not passing tests.
• Component-specific real HTTP/WebSocket, Redis, delegation, cancellation and negative-control evidence exists, but does not substitute for complete-head independent review or hosted checks.

This remains a draft. Fresh hosted checks, complete exact-diff independent review, current UI review evidence, resolved review threads and the repository's merge-policy disposition are required before landing. The active squash-only rule conflicts with the merge-only FORK.md contract. No protection or review gate is waived.

The fleet adapter in this candidate performs signed repository qualification, not AI inference. The separate durable bridge work is not deployed by this PR. Real Buzz-launched multi-host agent execution, provider fallbacks, physical-phone pairing and approvals, push/reconnect recovery and result inspection still require acceptance. Telegram replacement and production readiness are not established by this candidate.